Background

• When selectPlacements is called, placement attributes are written to the mParticle user profile and then forwarded to the Rokt kit, which merges profile attributes with the passed-in map before calling Rokt.execute().
• A fix in #585 ensured those user attributes were persisted before the kit ran, but that async wait was lost when Rokt handling moved into RoktKitApiImpl in #586.
• As a result, clients could see placement attributes missing in both mParticle and Rokt, especially when the kit reads from the user profile (e.g. Compose / prepareAttributesAsync flows).

What Has Changed

• Restored setRoktAttributesOnUser() in RoktKitApiImpl to persist placement attributes on the user and wait for TypedUserAttributeListener before delegating to the Rokt kit.
• Applied the same async wait to both selectPlacements and prepareAttributesAsync.
• Split attribute preparation into applyPlacementAttributeMapping(), ensureSandboxMode(), and setRoktAttributesOnUser() for clarity.
• Fixed case-sensitive email lookup in prepareAttributesAsync to use getValueIgnoreCase, matching selectPlacements.
• Added a unit test verifying the kit is not invoked until the user-attribute callback fires.

Checklist

• I have performed a self-review of my own code.
• I have made corresponding changes to the documentation.
• I have added tests that prove my fix is effective or that my feature works.
• I have tested this locally.

Reference Issue (For employees only. Ignore if you are an outside contributor)

• Closes https://go/j/[ticket-number]